Fix bad behaviour of xm when calling event.next(), by adding a different error
authorEwan Mellor <ewan@xensource.com>
Thu, 29 Mar 2007 15:18:39 +0000 (16:18 +0100)
committerEwan Mellor <ewan@xensource.com>
Thu, 29 Mar 2007 15:18:39 +0000 (16:18 +0100)
commitd05727902ff268894db2ac8950aefc1f0f470049
tree56ca3bdfc233849d1ac07447b7c6d53518c6cbe3
parentc7dfb7d1705933ce8fc7902a77303e4c48b57a58
Fix bad behaviour of xm when calling event.next(), by adding a different error
code (SESSION_NOT_REGISTERED).

Signed-off-by: Ewan Mellor <ewan@xensource.com>
docs/xen-api/xenapi-datamodel.tex
tools/python/xen/xend/XendAPI.py
tools/python/xen/xm/messages/en/xen-xm.po